The skill picker opens the mixed chooser (`includeFiles`), which renders
a tile per matching row. With no realm scope it fanned out across every
server realm — including large shared realms — so the picker stalled on
rendering and the intended skills may never appear.

Pass `realms: userRealmIdentifiers` so the picker searches only the user's
own workspaces, where the skills they attach live.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…lies

The skill menu scopes its mixed chooser to `realmServer.userRealmIdentifiers`.
Under mock matrix that list stayed empty (only `activeRealms` was set), so
the scope was a no-op and the chooser fanned out across every server realm —
including the large shared skills realm — and the intended skill tiles never
rendered in time.

Set `activeRealmServers` in the mock-matrix setup (as the workspace-chooser
integration test does) so the user realm list populates with the test realm,
exercising the same scoped path the skill menu takes in production.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Attachable skills live mostly in the shared Boxel Skills realm, which the
user-realms-only scope excluded, so they were not selectable. Scope the mixed
chooser to the user's own workspaces plus `skillsRealmURL`. Kept bounded
(rather than searching every server realm) so the federated search does not
stall on unrelated realms' contents.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

The skill chooser now searches the shared Boxel Skills realm as well as the
user's workspaces. In the e2e env that realm is indexed from scratch on server
startup, so the chooser's federated search stalls until it is ready and the
skill tests time out. Add a module-scoped `beforeAll` that waits (polling a
known public skill card) until the realm is served from its index before the
tests run. Scoped to this module so unrelated matrix suites don't pay the wait.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

The previous warm-up polled a single skill card, which is served before the
Boxel Skills realm finishes indexing — so the chooser's federated search still
stalled on the mid-index realm and the tests timed out. Poll `/_queue-status`
(monitoring-gated; bearer token = sha256('MONITORING' + realm-server seed))
until `pending: 0`, i.e. the whole realm-server index queue has drained, before
this module's tests run.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Root cause of the matrix skills failures (verified from the harness source, not
inferred): `support/isolated-realm-server.ts` marks `:4205/test/` and
`:4205/skills/` as catalog realms (`show_as_catalog = true`), and the skill
fixtures (e.g. `skill-pirate-speak`) live in `:4205/test/`. The scope was
`userRealmIdentifiers + skillsRealmURL`, which excludes catalog realms — so the
fixtures were never searched and the chooser showed nothing. The federated
search itself is fast (200 in ~100-200ms); indexing was never the issue (the
harness already gates tests on `_readiness-check`), so the queue-drain warm-up
is reverted.

Scope the chooser to user workspaces + catalog realms + the Boxel Skills realm.

Includes a temporary `[SKILL-SCOPE]` console.warn to confirm the resolved scope
in CI; will be removed once green.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Confirmed from the failing run's Playwright trace: the catalog-scope fix works
(the chooser shows "79 results across 2 realms" — Boxel Skills + Test Workspace
A), but the shared Boxel Skills realm contributes 76 skills that render first,
pushing the target test-realm skill below the fold — so its tile exists but is
not visible and the click times out.

Have `attachSkill` type the target's URL into the chooser search to narrow to
it before clicking (the same pattern messages.spec.ts already uses). Also drop
the temporary scope-diagnostic console.warn.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Root cause of the blank/unclickable skill tiles (confirmed live via DevTools):
the chooser set `initialFocusedSection` to the first selected realm, and
`isCollapsed` collapses every *other* realm's section to just its header
(`display:none` on its grid). Once the skill chooser scoped to multiple realms
(user + catalog + skills), the target skill's realm — not the first — was
collapsed, so its tile rendered at height 0 and the click timed out. (The old
chooser passed no realm scope, so nothing was focused or collapsed.)

Only auto-focus when the scope is a single realm (where collapsing is a no-op);
for a multi-realm scope, focus nothing so every section's results stay visible.
Verified in the running app: the target tile now renders at 252px, clickable.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>